Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Change back the precision of command duration to deciseconds instead of nanoseconds
Motivation and Context
The precision of command duration is not accurate with nanoseconds or microseconds.
Using deciseconds gave the best result when I initially developed this functionality.
Moreover, the current calculations are not valid:
deciseconds="$((10 - (command_start_deciseconds - current_time_deciseconds)))"
This can only be used accurately with deciseconds.
If anyone is interested, I can modify this PR to introduce a configuration giving user the choice of precision to use:
How Has This Been Tested?
Calculation have been verified and display has been tested with barbuk theme (cf screenshot).
Screenshots (if appropriate):
Before:
After:
Types of changes
Checklist:
clean_files.txt
and formatted it usinglint_clean_files.sh
.